Skip to content

fix(deps): update rust crate keyring to v3 #618

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update rust crate keyring to v3 #618

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 29, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
keyring dependencies major 2.3.3 -> 3.0.0

Release Notes

hwchen/keyring-rs (keyring)

v3.6.3

Compare Source

v3.6.2

Compare Source

  • Have docs.rs build docs for all modules on all platforms (thanks to @​unkcpz - see #​235).
  • Switch to fastrand for tests (see #​237).

v3.6.1

Compare Source

  • Updated dependencies; no code changes.

v3.6.0

Compare Source

  • Add combination keystore of keyutils and secret service (thanks to @​soywod).

v3.5.0

Compare Source

  • Add debug logging of internal operations (thanks to @​soywod).
  • Revert iOS security-framework dependency to v2 (see #​225).

v3.4.0

Compare Source

  • Allow use of both secret-service and keyutils.

v3.3.0

Compare Source

  • Add support for credential-store attributes other than those used by this crate. This allows the creation of credentials that are more compatible with 3rd-party clients, such as the OS-provided GUIs over credentials.
  • Make the textual descriptions of entries consistently follow the form user@service (or user@service:target if a target was specified).

v3.2.1

Compare Source

  • Re-enable access to v1 credentials. The fixes of version 3.2 meant that legacy credentials with no target attribute couldn't be accessed.

v3.2.0

Compare Source

  • Improve secret-service handling of targets, so that searches on locked items distinguish items with different targets properly.

v3.1.0

Compare Source

  • enhance the CLI to allow empty user names and better info about Ambiguous credentials.

v3.0.5

Compare Source

  • updated docs and clean up dead code. No code changes.

v3.0.4

Compare Source

  • expose a cross-platform module alias via the default module.

v3.0.3

Compare Source

  • fix feature linux-native, which was causing compile errors.

v3.0.2

Compare Source

  • add missing implementations for iOS set_secret and get_secret

v3.0.1

Compare Source

  • add back missing Sync trait on errors.

v3.0.0

Compare Source

  • add dbus-secret-service dependency to allow use on *n*x without an async runtime
  • (API change) rework feature controls on included keystores: now there is a feature for each keystore, and that keystore is included in a build if and only if its feature is specified and the keystore is supported by the target OS.
  • (API change) add direct support for setting and reading binary secret data, not just UTF-8 strings.

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Mar 29, 2025 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: src-tauri/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path src-tauri/Cargo.toml --package [email protected] --precise 3.6.3
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)

@renovate renovate bot force-pushed the renovate/keyring-3.x branch from 2396b67 to 8f9f6bd Compare June 15, 2025 08:01
@sonarqubecloud
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@renovate renovate bot force-pushed the renovate/keyring-3.x branch from 8f9f6bd to 2546317 Compare July 27, 2025 05:31
@sonarqubecloud
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@renovate renovate bot force-pushed the renovate/keyring-3.x branch from 2546317 to ae4ec0e Compare September 25, 2025 21:40
@sonarqubecloud
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants